AppID Key
Application
identifiers (AppIDs), group the configuration options, a set of named-values,
for one or more distributed COM objects into one centralized location in the
registry. Distributed COM objects hosted by the same executable are grouped
into one AppID to simplify the management of common security and
configuration settings. The HKEY_LOCAL_MACHINE\SOFTWARE\Classes key
corresponds to the HKEY_CLASSES_ROOT, which definition was retained for
compatibility with earlier versions of OLE.
Registry Entry
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\
{ AppID_value}\named_value
= value
Comments
AppIDs are
located in a newly created registry key hierarchy. The AppID_value is a
128-bit Globally Unique Identifier (GUID) that uniquely identifies the AppID.
AppIDs are
mapped to executables and classes using two different mechanisms.
Classes
indicate their corresponding AppID in their CLSID key. A named-value AppID
of type REG_SZ contains the string value corresponding to the AppID_value
under the AppID sub-key. This mapping is used during activation.
Executables
are registered under the AppID key in a named-value indicating the
module name (such as MYOLDAPP.EXE ). This named-value is of type REG_SZ and
contains the stringized AppID associated with the executable. This mapping is
used to obtain the default access permissions.
Named
Values:
|
\RemoteServerName = value |
Sets name
of remote server |
|
\ActivateAtStorage = value |
Configures
client to activate on same system as persistent storage |
|
\LocalService = value |
Sets the
application as a Win32 service |
|
\ServiceParameters = value |
Sets
parameters to be passed to a LocalService on invocation |
|
\RunAs = value |
Sets an
application to run only as a given user. |
|
\LaunchPermission = value |
Sets an ACL
that determines who can launch the application |
|
\AccessPermission = value |
Sets an ACL
that determines access |
See Also